Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1001

reference: 398-tree-1
name: 1001
tree-preservation-order: undefined
398-tpo-1
uprn
address-text
point: POINT (-1.017648 50.894828)
geometry: MULTIPOLYGON (((-1.017549 50.894817,-1.017554 50.894836,-1.017567 50.894854,-1.017589 50.894868,-1.017617 50.894877,-1.017647 50.894881,-1.017678 50.894878,-1.017706 50.894869,-1.017728 50.894855,-1.017743 50.894838,-1.017748 50.894819,-1.017744 50.894799,-1.017730 50.894781,-1.017708 50.894767,-1.017681 50.894758,-1.017650 50.894755,-1.017619 50.894758,-1.017591 50.894766,-1.017569 50.894780,-1.017554 50.894798,-1.017549 50.894817)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL